home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: OK, now what?
- Sent: 4/17/96 3:28 PM
- Received: 4/17/96 3:51 PM
- From: Henri Lamiraux, lamiraux@apple.com
- Reply-To: ODF-Interest@CILabs.ORG
- To: OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.
-
- >I do this all the time, I post a message and then, kinda find my answer,
- >but the question now is, how come, ODF swallows RequestEmbeddedFrame? I
- >posted my previous question and then searched through the source one more
- >time and came to the startling relization that it was swallowed in
- >FW_CEmbeddingFrame.
- >
- RequestEmbeddedFrame was not yet supported by ODF d11 (don't forget the
- version of ODF you have is a d release). ODFDraw or any other embedding
- parts build with ODF d11 is not supporting RequestEmbeddedFrame. ODF
- Release 1 is now supporting it and ODFDraw and ODFContainer behave
- correctly.
-
- >So if I drag my part into a non ODF Frame my second
- >frame is created.
- Which non-ODF embedding part are you using?
-
- >So how do I create the kind of frame that I want to that will work with
- >both ODF and non ODF parts? Or do I have to choose which one to work with?
- >
- >Jer,
- >
- You have to be aware that embedding part may decide to not support
- RequestEmbeddedFrame.For example the ODFEmbed part can only embed one
- frame at a time. ODFEmbed will never support RequestEmbeddedFrame. So as
- an embedded part you need to be aware of this case, RequestEmbeddedFrame
- may return null. Testing your part with containers that don't support
- RequestEmbeddedFrame is a goog idea.
-
- .......................................................................
- Henri Lamiraux lamiraux@apple.com
- Apple Computer, Inc. OpenDoc(tm) Development Framework
- .......................................................................
-
-
-